Digital asset validation prior to submission for network-based distribution

ABSTRACT

A system and method for submission of digital assets to a digital asset submission system are disclosed. The digital asset submission system can manage submissions of digital assets to a network-based distribution system. Submission of digital assets to the digital asset submission system can be performed over a network in a controlled manner such that the digital assets can be validated prior to transmission of the digital assets to the digital asset submission system. Advantageously, digital assets to be submitted for distribution can be substantially validated before the digital assets are transmitted to the digital asset submission system.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to submission of digital assets and, moreparticularly, to electronic submission of digital assets for purposes ofnetwork-based distribution.

2. Description of the Related Art

Today, online stores, such as the iTunes™ Store provided by Apple Inc.of Cupertino, Calif., allow customers (i.e., online users) via theInternet to purchase or rent media items (such as music, videos) orsoftware programs. Often, at online stores, numerous digital items aremade available and are provided by various different providers, such asmusic labels, movie companies, and application developers. Softwaretools, such as iProducer™ and iTunes Connect™ available from Apple Inc.,can assist providers with online submission of digital items to theiTunes™ Store.

Unfortunately, however, since submission involves transmission ofdigital files over the Internet to online stores for distribution, thesubmission process can be time consuming to a submitter. When thedigital files are large or voluminous, the transmission of the digitalfiles for the submission can take a substantial duration of time. Forexample, submission of a movie can take several hours. Even after thetime consuming transmission has been endured, the digital files of thesubmission may fail validation checks. As a result, the submitter mustcorrect the defects with respect to their prior submission and againattempt to submit the digital files. Consequently, there is a need forimproved approaches to render submission of digital files to onlinestores in a more efficient and reliable manner.

Therefore, there is a need for improved approaches to facilitatesubmission of digital assets for online distribution.

SUMMARY OF THE INVENTION

A system and method for submission of digital assets to a digital assetsubmission system are disclosed. The digital asset submission system canmanage submissions of digital assets to a network-based distributionsystem. Submission of digital assets to the digital asset submissionsystem can be performed over a network in a controlled manner such thatthe digital assets can be validated prior to transmission of the digitalassets to the digital asset submission system. Advantageously, digitalassets to be submitted for distribution can be substantially validatedbefore the digital assets are transmitted to the digital assetsubmission system. In one embodiment, a client computing device caninitially provide a summary for one or more digital assets to besubmitted. Then, a digital asset submission system can validate the oneor more digital assets based on the summary and validation rules. If thedigital asset submission system successfully validates the one or moredigital assets, final submission (e.g., transmission) of the digitalassets to the digital asset submission system is thereafter able to beperformed. On the other hand, if the digital asset submission systemdoes not successfully validate the one or more digital assets, finalsubmission of the digital assets to the digital asset submission systemis not performed.

The invention can be implemented in numerous ways, including as amethod, system, device, apparatus (including computer readable mediumand graphical user interface). Several embodiments of the invention arediscussed below.

According to one embodiment, a method for validating a digital assetpackage via a server computer is disclosed. The digital asset packagecan include at least a metadata file and one or more digital assetfiles. The method can, for example, include the operations of: receivingan initial validation submission including at least the metadata file;validating metadata within the metadata file; determining at least onedigital asset file identified in the metadata to be validated; sendingan initial validation response including at least a list of the at leastone digital asset file that is to be validated; receiving a subsequentvalidation submission including at least the metadata file and assetsummary information for the at least one digital asset file; determiningvalidation rules to be used in validating the at least one digital assetfile; validating the at least one digital asset file based on the assetsummary information and the determined validation rules; and sending asubsequent validation response in accordance with the validating of theat least one digital asset file.

According to one embodiment, a computer readable medium including atleast computer program code stored thereon for validating a digitalsubmission to a server computer via a data network is disclosed. Thedigital submission can include at least a metadata file and at least onedigital asset file. The computer readable medium can, for example,include at least: computer program code for receiving an assetvalidation submission including at least the metadata file and assetsummary information for the at least one digital asset file; computerprogram code for determining validation rules to be used in validatingthe at least one digital asset file; computer program code forvalidating the at least one digital asset file based on the assetsummary information and the determined validation rules; and computerprogram code for sending a validation response based on the validatingof the at least one digital asset file by the computer program code forvalidating the at least one digital asset file.

According to one embodiment, a method for submitting a digital assetpackage to a network-based server computer for validation is disclosed.The method can, for example, include at least the operations of: forminga digital asset package including at least a metadata file and digitalasset files; sending an initial validation submission including themetadata file to the server computer; receiving an initial validationresponse from the server computer, where the initial validation responseincludes at least a list of at least one digital asset file that is tobe described; producing at least one summary file for the at least onedigital asset file that is to be described; sending a subsequentvalidation submission including the at least one summary file to theserver computer; receiving a subsequent validation response from thesubmission server, the subsequent validation response including anindication of whether at least the at least one digital asset file hasbeen successfully validated; and thereafter submitting the digital assetpackage to the server computer if the subsequent validation responseindicates that at least the at least one digital asset file has beensuccessfully validated.

According to one embodiment, a computer readable medium including atleast computer program code stored thereon for submitting a digitalasset package to a network-based server computer for validation isdisclosed. The computer readable medium can, for example, includes atleast: computer program code for forming a digital asset packageincluding at least a metadata file and digital asset files; computerprogram code for producing at least asset summary information for atleast one of the digital asset files of the digital asset package;computer program code for sending an asset validation submissionincluding the asset summary information to the server computer; computerprogram code for receiving an asset validation response from thesubmission server, wherein the asset validation response includes anindication of whether at least the at least one digital asset file hasbeen successfully validated at the server computer based on the assetsummary information; and computer program code for submitting thedigital asset package to the server computer if the asset validationresponse indicates that at least the at least one digital asset file hasbeen successfully validated.

As a media system, one embodiment can include at least a digital packagesubmission subsystem configured to submit a digital asset package, and adigital package reception subsystem configured receive and process tothe digital asset package that has been submitted. The digital packagesubmission subsystem and the digital package reception system can beconnected via a computer data network. The digital package submissionsubsystem can be configured to at least: form a digital asset packageincluding at least a metadata file and digital asset files, produce atleast asset summary information for at least one of the digital assetfiles of the digital asset package, send an asset validation submissionincluding the asset summary information to the digital package receptionsubsystem, and receive an asset validation response from the digitalpackage reception subsystem. The asset validation response can includean indication of whether at least the at least one digital asset filehas been successfully validated at the digital package receptionsubsystem based on the asset summary information. Additionally, thedigital package submission subsystem can be configured to submit thedigital asset package to the server computer if the asset validationresponse indicates that at least the at least one digital asset file hasbeen successfully validated. The digital package reception subsystem isconfigured to at least: receive an asset validation submission includingat least the metadata file and the asset summary information for the atleast one digital asset file, determine validation rules to be used invalidating the at least one digital asset file, validate the at leastone digital asset file based on the asset summary information and thedetermined validation rules, and send a validation response inaccordance with the validating of the at least one digital asset file bythe computer program code for validating the at least one digital assetfile.

Other aspects and advantages of the invention will become apparent fromthe following detailed description taken in conjunction with theaccompanying drawings which illustrate, by way of example, theprinciples of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be readily understood by the following detaileddescription in conjunction with the accompanying drawings, wherein likereference numerals designate like elements, and in which:

FIG. 1 is a block diagram of a digital asset submission and distributionsystem according to one embodiment of the invention.

FIG. 2 is a flow diagram of a client validation process according to oneembodiment of the invention.

FIG. 3 is a flow diagram of a server validation process according to oneembodiment of the invention.

FIGS. 4A and 4B are flow diagrams of a client submission processaccording to one embodiment of the invention.

FIGS. 5A-5C are flow diagrams of a server submission process accordingto one embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

A system and method for submission of digital assets to a digital assetsubmission system are disclosed. The digital asset submission system canmanage submissions of digital assets to a network-based distributionsystem. Submission of digital assets to the digital asset submissionsystem can be performed over a network in a controlled manner such thatthe digital assets can be validated prior to transmission of the digitalassets to the digital asset submission system. Advantageously, digitalassets to be submitted for distribution can be substantially validatedbefore the digital assets are transmitted to the digital assetsubmission system. In one embodiment, a client computing device caninitially provide a summary for one or more digital assets to besubmitted. Then, a digital asset submission system can validate the oneor more digital assets based on the summary and validation rules. If thedigital asset submission system successfully validates the one or moredigital assets, final submission (e.g., transmission) of the digitalassets to the digital asset submission system is thereafter able to beperformed. On the other hand, if the digital asset submission systemdoes not successfully validate the one or more digital assets, finalsubmission of the digital assets to the digital asset submission systemis not performed.

Embodiments of various aspects of the invention are discussed below withreference to FIGS. 1-5C. However, those skilled in the art will readilyappreciate that the detailed description given herein with respect tothese figures is for explanatory purposes as the invention extendsbeyond these limited embodiments.

FIG. 1 is a block diagram of a digital asset submission and distributionsystem 100 according to one embodiment of the invention. The digitalasset submission and distribution system 100 includes a digital assetdistribution site 102. The digital asset distribution site 102 providesan online access point for distribution of various digital assets. Forexample, the digital asset distribution site 102 can be referred to asan online store. A digital asset submission and management system 104operates to receive submissions of digital assets from various digitalasset submitters. The digital asset submission and management system 104can process submission of digital assets and authorize distribution ofapproved digital assets. The digital assets can be stored in a digitalasset storage device 106. In one embodiment, the digital asset storagedevice 106 includes a mass data store and one or more databases. Thedigital asset storage device 106 provides mass storage of the numerousdigital assets that are available for distribution (e.g., purchase orrental). For example, digital assets that have been purchased can beaccessed from the digital asset storage device 106 over a data network108 by way of the digital asset distribution site 102. Examples ofdigital assets include digital media assets (e.g., media items) orcomputer program products. Digital media assets can pertain to music(e.g., songs or albums) or video (e.g., movies or television shows).Computer program products can pertain to applications (or applicationprograms), animations, or presentations.

The digital asset submission and distribution system 100 also includes afirst client 110 and a second client 112. Typically, the digital assetsubmission and distribution system 100 would include a plurality ofdifferent clients 110, 112. The first client 110 includes a networkaccess program 114. The second client 112 includes a digital assetsubmission program 116. Some clients can also include both the networkaccess program 114 and the digital asset submission program 116. Thenetwork access program 114 is an application program (e.g., softwareapplication) that operates on the first client 110, which is a computingdevice. One example of a suitable network access program is a networkbrowser (e.g., Microsoft Explorer or Safari). Another example of asuitable network access program is iTunes™ offered by Apple Inc. Thefirst client 110 is coupled to the digital asset distribution site 102through the data network 108. Hence, any of the first clients 110 caninteract with the digital asset distribution site 102 to review,purchase and/or manage digital assets.

The digital asset submission program 116 is also an application program(e.g., software application) that operates on the second client 112,which is a computing device. The digital asset submission program 116 isused to submit digital assets to the digital asset submission andmanagement system 104 for eventual distribution by the mediadistribution site 102. Although the network access program 114 and thedigital asset submission program 116 are shown in FIG. 1 as separateprograms, it should be understood that such programs can be integratedinto a single program or reside on the same client machine.

In the digital asset submission and distribution system 100 shown inFIG. 1, the digital assets are submitted to the digital asset submissionand management system 104 by way of the digital asset submission program116. The digital assets that have been submitted (e.g., via the secondclient 112 are processed and then stored in the digital asset storagedevice 106. Thereafter, the stored digital assets are available to bepurchased from the digital asset distribution site 102. Upon purchasinga particular digital asset, the digital asset distribution site 102permits the digital data for the particular digital asset to beretrieved from the digital asset storage device 106 and then delivered(e.g., downloaded) from the digital asset distribution site 102 to therequesting client 110 through the data network 108. In this regard, thedigital asset distribution site 102 or some other delivery server (notshown) obtains the digital data corresponding to the particular digitalasset from the digital asset storage device 106 and downloads suchdigital data through the data network 108 to the client 110. Thedownloaded digital data can then be stored on the client 110. In oneembodiment, the downloaded digital data is encrypted as received at theclient 110 but is decrypted and then perhaps re-encrypted beforepersistently stored on the client 110. Thereafter, the client 110 canutilize (e.g., execute) the digital data of the digital asset at theclient 110.

The digital asset submission and distribution system 100 allows a userof the client 110 to utilize the network access program 114 to browse,search or sort through a plurality of digital assets that can bepurchased from the digital asset distribution site 102. The networkaccess program 114 may also allow the user to preview or demo some orall of a digital asset. In the event that the user of the network accessprogram 114 desires to purchase a particular digital asset, the user(via the network access program 114) and the digital asset distributionsite 102 can engage in an online commerce transaction in which the userpays for access rights to the particular digital asset.

The submission and purchase of the digital assets can be achieved overthe data network 108. In other words, the submission and purchase of thedigital assets can be achieved online. The purchase of media itemsonline can also be referred to as electronic commerce (e-commerce). Inone embodiment, the data network 108 includes at least a portion of theInternet. The clients 110, 112 can vary with application but generallyare computing devices that have memory storage. Often, the clients 110,112 are personal computers or other computing devices that are capableof storing and presenting media to their users. In one embodiment, theconnections through the data network 108 between the digital assetdistribution site 102 and the clients 110, 112 can be through secureconnections, such as Secure Sockets Layer (SSL).

Although the digital asset distribution site 102, the digital assetsubmission and management system 104 and the digital asset storagedevice 106 are shown in FIG. 1 as being separate components, it shouldbe understood that any of these components can be combined into one ormore apparatus. For example, the digital asset submission and managementsystem 104 can be incorporated into the digital asset distribution site102. As another example, the digital asset storage device 106 can beincorporated into the digital asset distribution site 102 or the digitalasset submission and management system 104.

The client (or client device) can, for example, be a computing device.Examples of a computing device include a personal computer (e.g.,desktop computer, notebook computer or netbook computer), or a portablehandheld electronic device (e.g., Portable Digital Assistant (PDA),multi-function mobile telephone).

FIG. 2 is a flow diagram of a client validation process 200 according toone embodiment of the invention. The client validation process 200 can,for example, be performed by a computing device, such as the client 112illustrated in FIG. 1. As an example, the client validation process 200can be performed by the digital asset submission program 116 operatingon the client 112.

The client validation process 200 can form 202 a digital asset packageincluding at least a metadata file and digital asset files. Typically, auser of the computing device can participate in forming the digitalasset package by providing metadata and identifying digital assets to beincluded. To facilitate validation of the digital asset files, at leastone summary file for at least one of the digital asset files can beproduced 204. Next, an asset validation submission can be sent 206 to aserver computer for validation. Here, the asset validation submissionthat is sent 206 includes the at least one summary file that has beenproduced 204 for the at least one of the digital asset files.

After the asset validation submission has been sent 206, a decision 208can determine whether an asset validation response has been received.The server computer can process the asset validation submission andprovide an asset validation response. When the decision 208 determinesthat an asset validation response has not yet been received, the clientvalidation process 200 can await such a response.

Once the decision 208 determines that an asset validation response hasbeen received, a decision 210 can determine whether validation has beensuccessful. In other words, the asset validation response can include anindication of whether or not the validation of the at least one digitalasset file within the digital asset package has been successful. Whenthe decision 210 determines that such validation has been successful,the digital asset package may be submitted 212 to the server computer,thereby formally submitting the digital asset package. The formal (orfull) submission typically includes the entire digital asset packingsuch as including the metadata file as well as the digital asset files.On the other hand, when the decision 210 determines that such validationhas not been successful, submission of the digital asset package can bedenied 214. Following the blocks 212 and 214, the client validationprocess 200 can end.

FIG. 3 is a flow diagram of a server validation process 300 according toone embodiment of the invention. The server validation process 300 can,for example, be performed by a server computer, such as the digitalasset submission and management system 104 illustrated in FIG. 1 or someother server computer. The server validation process 300 can representcounterpart processing to the client validation process 200 illustratedin FIG. 2.

The server validation process 300 can begin with a decision 302 thatdetermines whether an asset validation submission has been received.Here, the decision 302 determines whether the server computer hasreceived an asset validation submission from a client computing device(e.g., the client device). When the decision 302 determines that anasset validation submission has not been received, the server validationprocess 300 awaits such a submission. In other words, the servervalidation process 300 can be deemed invoked when an asset validationsubmission has been received at the server computer.

In any case, when the decision 302 determines that an asset validationsubmission has been received, validation rules to be used can bedetermined 304. Additionally, one or more digital asset files can bevalidated 306 based on one or more summary files and the determinedvalidation rules. The asset validation submission includes one or moresummary files that are used to validate 306 the corresponding one ormore digital asset file. After the one or more digital asset files havebeen validated 306, a validation response can be sent 308 to the clientcomputing device that provided the asset validation submission.

FIGS. 4A and 4B are flow diagrams of a client submission process 400according to one embodiment of the invention. The client submissionprocess 400 is, for example, performed by a client computing device,such as the client 112 illustrated in FIG. 1.

The client submission process 400 can initially provide 402 a digitalasset package that includes at least a metadata file and digital assetfiles. The digital asset package can be formed at the client computingdevice or can be formed elsewhere and uploaded to the client computingdevice. Although the metadata can vary depending on the type of digitalmedia asset, the metadata within the metadata file can, for example,include one or more of: a digital asset type, digital asset title/name,digital asset identifier, a production company, copyright information,release date, supported device type indication, genre indication,version number, artist(s)/actor(s) identifiers, sales start date, filename(s), support information, license agreement information, etc. Thedigital asset files can, for example, pertain to digital media assets(e.g., media items) or computer program products (e.g., applicationprograms). In forming the digital asset package, one or more digitalelectronic files can be uploaded to the client computing device.

An initial validation submission with the metadata file can be sent 404to a submission server. The submission server is a computing device thatis utilized to process the validation submission. After the initialvalidation submission has been sent 404, a decision 406 can determinewhether an initial validation response has been received from thesubmission server. When the decision 406 determines that an initialvalidation response has not been received, a decision 408 can determinewhether the client submission process 400 should quit or end. When thedecision 408 determines that the client submission process should quitor end, then the client submission process 400 can end. Alternatively,when the decision 408 determines that the client submission process 400should not quit or end, the client submission process 400 returns torepeat the decision 406 to await the receipt of an initial validationresponse.

Once the decision 406 determines that an initial validation response hasbeen received, a decision 410 can determine whether any digital assetfiles associated with the digital asset package are to be described. Forexample, the determination can be based on the metadata and/or fileextensions for the digital asset files. In one embodiment, the initialvalidation response provides a list of one or more digital asset filesthat are to be described at the client computing device for purposes offurther validation. When the decision 410 determines that one or moredigital asset files are to be described, the one or more digital assetfiles are then examined 412 to produce one or more summary files. In oneembodiment, a single summary file can be utilized to summarize one ormore digital asset files. In another embodiment, separate summary filesare produced for each of the one or more digital asset files beingsummarized. The summary files contain information regarding header orcontent portions of the digital asset files as obtained throughexamination of such digital asset files.

Next, a subsequent validation submission with metadata and one or moresummary files can be sent 414 to the submission server. Here, additionalvalidation is being performed or requested with respect to one or moredigital asset files of the digital asset package. However, it should berecognized that the digital asset files are not, at this time, beingsent to the submission server. Instead, the one or more summary filesare provided to the submission server for use in performing validationof the one or more digital asset files.

Next, a decision 416 determines whether a subsequent validation responsehas been received from the submission server. When the decision 416determines that a subsequent validation response has not been received,a decision 418 determines whether the client submission process 400should quit or end. When the decision 418 determines that the clientsubmission process 400 should quit or end, the client submission process400 can end. On the other hand, when the decision 418 determines thatthe client submission process 400 should not quit or end, the processingreturns to repeat the decision 416 so as to wait a subsequent validationresponse.

Once the decision 416 determines that a subsequent validation responsehas been received, a decision 420 can determine whether the subsequentvalidation response indicates any errors or warnings with respect to thevalidation of the one or more digital asset files within the digitalasset package (namely, those digital asset files that were summarized bya summary file). When the decision 420 determines that there are errorsor warnings specified by the subsequent validation response, the errorsor warnings can be displayed 422. Here, the errors or warnings can bedisplayed 422 on a display device associated with the client computingdevice. Alternatively, when the decision 420 determines that there areno errors or warnings specified by the subsequent validation response,the block 422 can be bypassed.

Following the block 422 or its being bypassed, a decision 420 candetermine whether there are any errors present. Specifically, thedecision 424 can determine whether the subsequent validation responsespecifies any errors, namely, validation errors. When the decision 424determines that there are errors present, the submission of the digitalasset package can be denied 426. Alternatively, when the decision 424determines that there are no errors present, the digital asset packagecan be submitted 428 to the submission server. At this time, the digitalasset package can be transmitted from the client computing device to thesubmission server over one or more networks. The digital asset packagebeing submitted includes not only the metadata file but also the one ormore digital asset files included within the digital asset package. Inthis case, prior processing has provide for validation of metadata(initial validation) as well as for validation of digital assets(subsequent validation). As such, the digital asset package is onlysubmitted 428 after significant validation has been successfullyperformed. Following the blocks 426 and 428, the client submissionprocess 400 can end.

FIGS. 5A-5C are flow diagrams of a server submission process 500according to one embodiment of the invention. The server submissionprocess 500 can, for example, be performed by a server computer, such asthe digital asset submission and management system 104 illustrated inFIG. 1 or some other server computer. The server submission process 500can represent counterpart processing to the client submission process400 illustrated in FIGS. 4A and 4B.

The server submission process 500 can begin with a decision 502 thatdetermines whether an initial validation submission has been received.When the decision 502 determines that an initial validation submissionhas been received (such as from a client computing device), initialvalidation can be performed at the server computer. Specifically,metadata submitted with the initial validation submission can bevalidated 504. In addition, one or more digital asset files identifiedin the metadata that are to be further validated can be determined 506.Here, the server computer can analyze the metadata to decide andidentify one or more digital asset files identified therein for whichfurther validation is to be performed. Then, an initial validationresponse including a list of the determined digital asset files to befurther validated can be sent 508 to the client computing device.Further, in the event that in the decision 502 determines that aninitial validation submission has not been received, the blocks 504-508can be bypassed since there is no initial validation to be performed.

Following the block 508 or its being bypassed, a decision 510 candetermine whether a subsequent validation submission has been received.Here, the server computer can determine whether a subsequent validationsubmission has been received from a client computing device. When thedecision 510 determines that a subsequent validation submission has beenreceived, the subsequent validation processing can be performed at theserver computer. Specifically, validation rules to be used can bedetermined 512. The validation rules can be determined based on variouscriteria. For example, the validation rules can be determined 512 basedon a type of digital asset to be validated. As another example, thevalidation rules can be determined 512 based on the submitter of the oneor more digital assets. In other words, the validation rules aredetermined 512 at the server computer but the validation rules can bedependent on one or more criteria, such as type of digital asset, typeof submission, particular submitter, and/or type of submitter. Next, theone or more digital asset files can be validated 514 based on the one ormore summary files and the determine validation rules. Here, using thedetermined validation rules, the one or more summary files can beanalyzed to determine whether the one or more associated digital assetfiles can be validated 514. A decision 516 can then determine whetherthere are any errors or warnings as a result of the validation 514. Whenthe decision 516 determines that there are errors or warnings, asubsequent validation response can be formed 520 including the errors orwarnings. Alternatively, when the decision 516 determines that thevalidation 514 does not result in any errors or warnings, a subsequentvalidation response can be formed 518 without errors or warnings.Following the blocks 518 and 520, a subsequent validation response canbe sent 522 to the client computing device. Further, in the event thatthe decision 510 determines that a subsequent validation submission hasnot been received, the blocks 512-522 can be bypassed.

Following the block 522 or its being bypassed, a decision 524 candetermine whether a validated submission has been received. When thedecision 524 determines that a validated submission has been received, adecision 526 can determine whether the submission has been successfullyvalidated. Here, the submission being received from the client computingdevice is the submission of the digital asset package. In order for thesubmission of the digital asset package to be considered, the digitalasset package must have been properly validated. In order for thedigital asset package to be considered properly validated, the digitalasset package must have successfully passed the initial validation aswell as the subsequent validation. As noted above, the initialvalidation primarily concerns validation of the metadata, while thesubsequent validation primarily concerns validation of the one and moredigital asset files. When the decision 526 determines that the digitalasset package being submitted has not been successfully validated, thesubmission is declined 528. On the other hand, when the decision 526determines that the digital asset package being submitted has beensuccessfully validated, the submission is accepted 530. Accordingly, theserver submission process 500 only permits submission of digital assetpackages that have been successfully validated. Following the blocks 528and 530, as well as following the decision 524 when it is determinedthat a validated submission has not been received, the server submissionprocess 500 can return to repeat the decision 502 so that additionalsubmissions can be processed in a similar manner.

This application also references and/or incorporates: (1) U.S. patentapplication Ser. No. 11/712,304, filed Feb. 27, 2007, and entitled“Submission Of Metadata Content And Media Content To A MediaDistribution System”, which is hereby incorporated herein by reference;(2) U.S. patent application Ser. No. 11/712,303, filed Feb. 27, 2007,and entitled “Processing Of Metadata Content And Media Content ReceivedBy A Media Distribution System”, which is hereby incorporated herein byreference; and (3) U.S. patent application Ser. No. 12/538,050, filedAug. 7, 2009, and entitled “Automatic Transport Discovery for MediaSubmission”, which is hereby incorporated herein by reference.

The various aspects, features, embodiments or implementations of theinvention described above can be used alone or in various combinations.

Embodiments of the invention can, for example, be implemented bysoftware, hardware, or a combination of hardware and software.Embodiments of the invention can also be embodied as computer readablecode on a computer readable medium. The computer readable medium is anydata storage device that can store data which can thereafter be read bya computer system. Examples of the computer readable medium generallyinclude read-only memory and random-access memory. More specificexamples of computer readable medium are tangible and include Flashmemory, EEPROM memory, memory card, CD-ROM, DVD, hard drive, magnetictape, and optical data storage device. The computer readable medium canalso be distributed over network-coupled computer systems so that thecomputer readable code is stored and executed in a distributed fashion.

The many features and advantages of the present invention are apparentfrom the written description. Further, since numerous modifications andchanges will readily occur to those skilled in the art, the inventionshould not be limited to the exact construction and operation asillustrated and described. Hence, all suitable modifications andequivalents may be resorted to as falling within the scope of theinvention.

1. A method for validating a digital asset package via a servercomputer, the digital asset package including at least a metadata fileand one or more digital asset files, the method comprising: receiving,from a client device, an initial validation submission including atleast the metadata file; validating metadata within the metadata file;determining at least one digital asset file identified in the metadatato be validated; sending, to the client device, an initial validationresponse including at least a list of the at least one digital assetfile that is to be validated; receiving, from the client device, asubsequent validation submission including at least the metadata fileand asset summary information for the at least one digital asset file;determining validation rules to be used in validating the at least onedigital asset file; validating the at least one digital asset file basedon the asset summary information and the determined validation rules;and sending, to the client device, a subsequent validation response inaccordance with the validating of the at least one digital asset file.2. A method as recited in claim 1, wherein the list included in theinitial validation response identifies a plurality of digital assetfiles, and wherein the metadata in the metadata file is descriptive ofeach of the plurality of digital asset files.
 3. A method as recited inclaim 2, wherein the determining of the validation rules comprises:determining an asset type for each of the plurality of digital assetfiles; and determining a different validation rule set for each of theasset types.
 4. A method as recited in claim 3, wherein the validatingof the at least one digital asset file validates each of the pluralityof digital asset files using the validation rules appropriate for thecorresponding asset type of the digital asset files.
 5. A method asrecited in claim 1, wherein the subsequent validation response includesan indication of at least one error or warning with respect to thevalidation of the at least one digital asset file.
 6. A method asrecited in claim 1, wherein the determining of the at least one digitalasset file identified in the metadata to be validated comprises:examining the metadata to identify the at least one digital asset file;and determining the at least one digital asset file identified in themetadata based on the examining of the metadata.
 7. A method as recitedin claim 1, wherein the determining of the at least one digital assetfile is based on the metadata and on a file extension for the at leastone digital asset file.
 8. A method as recited in claim 1, wherein theat least one the digital asset file is a media asset file.
 9. A methodas recited in claim 1, wherein said method further comprises: acceptingsubmission, from the client device, of the digital submission if thevalidating successfully validates the metadata as well as the at leastone digital asset file.
 10. A computer readable medium including atleast computer program code stored thereon for validating a digitalsubmission to a server computer via a data network, the digitalsubmission including at least a metadata file and at least one digitalasset file, the computer readable medium comprising: computer programcode for receiving an asset validation submission including at least themetadata file and asset summary information for the at least one digitalasset file; computer program code for determining validation rules to beused in validating the at least one digital asset file; computer programcode for validating the at least one digital asset file based on theasset summary information and the determined validation rules; andcomputer program code for sending a validation response based on thevalidating of the at least one digital asset file by the computerprogram code for validating the at least one digital asset file.
 11. Acomputer readable medium as recited in claim 10, wherein said computerreadable medium further comprises: computer program code for acceptingsubmission, from the client device, of the digital submission if thecomputer program code for validating successfully validates the at leastone digital asset file.
 12. A computer readable medium as recited inclaim 11, wherein said computer readable medium further comprises:computer program code for receiving a metadata validation submissionincluding at least the metadata file; computer program code forvalidating metadata within the metadata file; computer program code fordetermining the at least one digital asset file identified in themetadata to be validated; and computer program code for sending ametadata validation response including at least a list of the at leastone digital asset file that is to be validated.
 13. A method forsubmitting a digital asset package to a network-based server computerfor validation, the method comprising: forming a digital asset packageincluding at least a metadata file and digital asset files; sending aninitial validation submission including the metadata file to the servercomputer; receiving an initial validation response from the servercomputer, the initial validation response including at least a list ofat least one digital asset file that is to be described; producing atleast one summary file for the at least one digital asset file that isto be described; sending a subsequent validation submission includingthe at least one summary file to the server computer; receiving asubsequent validation response from the submission server, thesubsequent validation response including an indication of whether atleast the at least one digital asset file has been successfullyvalidated; and thereafter submitting the digital asset package to theserver computer if the subsequent validation response indicates that atleast the at least one digital asset file has been successfullyvalidated.
 14. A method as recited in claim 13, wherein the producing ofthe at least one summary file includes examining digital data within theat least one digital asset file.
 15. A method as recited in claim 13,wherein the at least one digital asset file includes at least a headerportion and a data portion, and wherein the producing of the at leastone summary file includes examining the digital data residing in theheader portion and the data portion of the at least one digital assetfile.
 16. A method as recited in claim 15, wherein the at least onesummary file is a markup language file.
 17. A method as recited in claim13, wherein the initial validation response includes at least a list ofa plurality of digital asset files to be described, and wherein theproducing produces a separate summary file for each of the plurality ofdigital assets.
 18. A computer readable medium including at leastcomputer program code stored thereon for submitting a digital assetpackage to a network-based server computer for validation, the computerreadable medium comprising: computer program code for forming a digitalasset package including at least a metadata file and digital assetfiles; computer program code for producing at least asset summaryinformation for at least one of the digital asset files of the digitalasset package; computer program code for sending an asset validationsubmission including the asset summary information to the servercomputer; computer program code for receiving an asset validationresponse from the submission server, the asset validation responseincluding an indication of whether at least the at least one digitalasset file has been successfully validated at the server computer basedon the asset summary information; and computer program code forsubmitting the digital asset package to the server computer if the assetvalidation response indicates that at least the at least one digitalasset file has been successfully validated.
 19. A computer readablemedium as recited in claim 18, wherein the at least one digital assetfile includes at least a header portion and a data portion, and whereinthe computer program code for producing the at least one asset summaryinformation includes computer program code for examining the digitaldata residing in the header portion and the data portion of the at leastone digital asset file.
 20. A media system, comprising: a digitalpackage submission subsystem configured to submit a digital assetpackage; and a digital package reception subsystem configured receiveand process to the digital asset package that has been submitted,wherein the digital package submission subsystem and the digital packagereception system are operatively connectable via a computer datanetwork, wherein the digital package submission subsystem is configuredto at least: form a digital asset package including at least a metadatafile and digital asset files; produce at least asset summary informationfor at least one of the digital asset files of the digital assetpackage; send an asset validation submission including the asset summaryinformation to the digital package reception subsystem; receive an assetvalidation response from the digital package reception subsystem, theasset validation response including an indication of whether at leastthe at least one digital asset file has been successfully validated atthe digital package reception subsystem based on the asset summaryinformation; and submit the digital asset package to the server computerif the asset validation response indicates that at least the at leastone digital asset file has been successfully validated, and wherein thedigital package reception subsystem is configured to at least: receivean asset validation submission including at least the metadata file andthe asset summary information for the at least one digital asset file;determine validation rules to be used in validating the at least onedigital asset file; validate the at least one digital asset file basedon the asset summary information and the determined validation rules;and send a validation response in accordance with the validating of theat least one digital asset file by the computer program code forvalidating the at least one digital asset file.